Release 10.1A: OpenEdge Development:
Debugging and Troubleshooting

How Progress handles failure conditions

Table 7–1 summarizes the types of failures you might encounter and the diagnostic information that results.

Table 7–1: Program failures and resulting dump files 

This type of failure	Provides this diagnostic information
Progress C code detects a fatal error, such as an out-of-memory condition.	A procore file. Additionally, if the message is marked as coredump: Windows — protrace file. UNIX — protrace and core files.
An exception occurs in Progress Java code (for example, broker, NameServer, WebSpeed Messenger).	A stack trace written to the log file. The broker continues to run for threads associated with other clients.
Memory violation.	Windows — protrace file; Dr. Watson log, if set in the registry. UNIX — procore, protrace, and core files.
OpenEdge executable hangs; you must terminate it using the kill command or the Task Manager.	Windows — None (usually, waiting for an event that never occurs; in an infinite loop; or a GPF occurs that hangs during failure processing). UNIX — protrace file, if you send a SIGUSR1 to the process as part of the kill operation.